This chapter describes how to use the software. It consists of:
When typing a command, remember the following:
When you start the device, the console displays a boot message. The OPCON prompt (*) then appears on the screen indicating that you are in the OPCON process and you can begin entering OPCON commands. This is the command prompt from which you communicate with different processes.
Commands that are needed more often appear before the "- - - - -" separator. Enter the appropriate command at the OPCON prompt (*). See Table 11 for a list of commands.
Alternatively, you can:
The status command displays information about the device processes, such as the process IDs (PIDs), process names and status of the process. Issuing the status command is shown in the following example:
| Note: | Not every process listed has a user interface (for example, the talk 3 process). The talk 4 command is for use by IBM service representatives. |
Each process uses a different prompt. You can tell which process your console is connected to by looking at the prompt. (If the prompt does not appear when you enter the talk pid command, press Enter again.)
The following list shows the prompts for the five main processes:
Table 1. Processes, Their Purpose, and Commands to Access
| Process | Level and Purpose | Command to Access | Input Prompt | ||
|---|---|---|---|---|---|
| OPCON | Level 1 - access to all secondary levels | Ctrl-P | asterisk (*) | ||
| CONFIG | Level 2 - base services configuration and access to configuration third level | Configuration or talk 6 | Config > | ||
| GWCON | Level 2 - base services operation and monitoring and access to operations and monitoring on third level | Console or talk 5 | plus sign (+) | ||
| MONITR | Level 2 - message display | Event or talk 2 | (none) | ||
| ELSCon | Level 2 - direct monitoring and access to ELS console | els or talk 7 | ELS Secondary Console> | ||
| MOSDBG | Level 2 - diagnostic environment | talk 4 | db> | ||
| |||||
At the OPCON prompt level, you can begin to enter commands from the keyboard. Use the Backspace key to delete the last character typed in on the command line. Use Ctrl-U to delete the whole command line entry so that you can reenter a command. See "Command Completion" and "Command History" for additional details or press Escape ?.
At the command prompts, you can obtain help in the form of a listing of the commands available at that level. To do this, type ? (the help command), and then press Enter. Use ? to list the commands that are available from the current level. You can usually enter a ? after a specific command name to list its options.
For example, the following information appears if you enter ? at the * prompt:
*?
CONFIGURATION (Talk 6)
CONSOLE (Talk 5)
EVENT Logging System (Talk 2)
ELS Console (Talk 7)
LOGOUT
PING (IP-Address)
RELOAD
RESTART
TELNET to IP-Address (this terminal type)
-----------------------------------------------
DIVERT output from process
FLUSH output from process
HALT output from process
INTERCEPT character is
MEMORY statistics
STATUS of Processes(es)
TALK to process
(you may cycle through these commands by pressing the TAB key)
The multiple-level nature of the software places you in secondary, tertiary, and even lower level environments as you configure or operate the 8371. To return to the next higher level, enter the exit command. To get to the secondary level, continue entering exit until you receive the secondary level prompt (either Config> or +).
For example, to exit the ASRT protocol configuration process:
ASRT config> exit Config>
If you need to get to the primary level (OPCON), enter the intercept character (Ctrl-P by default).
To get back to the OPCON prompt (*), press Ctrl-P. You must always return to OPCON before you can communicate with another process. For example, if you are connected to the console (GWCON) process and you want to connect to the CONFIG process, you must press Ctrl-P to return to OPCON first. The Ctrl-P key combination is the default intercept character.
If you use the intercept character from a third-level or lower level menu to return to the * prompt, the next time you use the talk command to talk to the same process, you will reenter that same level menu. This link goes away when the device is re-initialized.
All interfaces, features, and protocols have commands that you use to access the following processes:
You can also configure or operate some base system services through the second-level processes. The commands to perform these functions are described starting in What is CONFIG?.
The next sections describe the procedures for accessing the second-level processes.
Each protocol configuration process is accessed through the device's CONFIG process. CONFIG is the second-level process of the device user interface that lets you communicate with third-level processes. Protocol processes are examples of third-level processes.
The CONFIG command interface is made up of levels of menus. Protocol configuration command interfaces are menus within the CONFIG interface. Each protocol configuration interface has its own prompt. For example, the prompt for the SNMP protocol command interface is SNMP config>.
The next sections describe these procedures in more detail.
To enter the CONFIG process from OPCON and obtain the CONFIG prompt, enter the configuration command. Alternatively, you can enter the OPCON talk command and the PID for CONFIG. The PID for CONFIG is 6.
* configuration
or
* talk 6
The console displays the CONFIG prompt (Config>). If the prompt does not appear, press the Enter key again.
Changes that you make to the protocol parameters through CONFIG do not take effect until you either activate the net that contains any dynamic changes or reload the device software.
To reload the device, enter the OPCON reload command. For example:
* reload Are you sure you want to reload the gateway? (Yes or No): yes
To view information about the interfaces, features, or protocols or to change parameters while running, you must access and use the operating (monitoring) process. Operating command interfaces are modes of the GWCON interface. Within the GWCON mode, each interface, feature, or protocol interface has its own prompt. For example, the prompt for the SNMP protocol is SNMP>.
| Note: | Any parameters you change in this process will not remain active across any event that causes the 8371 to reload the operational code, such as a power outage or entering the reload command. |
The next sections describe these procedures in more detail.
To enter the GWCON process from OPCON and obtain the GWCON prompt, enter the console command. Alternatively, you may enter the talk command and the PID for GWCON. The PID for GWCON is 5. For example:
* console
or
* talk 5
The GWCON prompt (+) then displays on the console. If the prompt does not appear, press Enter again.
The Secondary ELS Console provides convenient access to GWCON talk 5 ELS without disrupting the current state of GWCON. You may be in the middle of a ping in talk 5, or deep inside a talk 5 menu structure, and want to control ELS without disrupting the current state of GWCON. The secondary ELS console (Talk 7) serves this purpose.
To enter the Secondary ELS Console (ELScon) process from OPCON and obtain the Secondary ELS Console prompt, enter the els command. Alternatively, you may enter the talk 7 command.
In the following example, another ELS event is displayed while performing a ping command.
| Note: | The intercept character (Ctrl-P by default) is used to obtain the OPCON prompt (*). |
*talk 5
+protocol hst
HST>ping 10.0.0.9
PING 10.0.0.2 -> 10.0.0.9: 56 data bytes, ttl=64, every 1 sec.
*talk 7
ELS Secondary Console>display event ip.7
Complete
ELS Secondary Console>
*talk 2
00:20:48 IP.007: 10.0.0.2 -> 10.0.0.9
00:20:49 IP.007: 10.0.0.2 -> 10.0.0.9
After accessing the second level, you must enter commands on the third level to configure or operate the interfaces, features, and protocols in your IBM 8371. The following sections describe how to access the third level processes.
To help you access the IBM 8371 feature configuration and operating processes, this section outlines both of these procedures.
Use the feature command from the CONFIG process to access configuration commands for specific IBM 8371 features outside of the protocol and network interface configuration processes.
Use the feature command from the GWCON process to access console commands for specific features that are outside of the protocol and network interface console processes.
Enter a question mark after the feature command to display a listing of the features available for your software release. For example:
Config> feature ?
QOS
Self Learning IP
RMON
Feature name or number [Self Learning IP] ?
To access a particular feature's configuration or operating prompt, enter the feature command at the Config> or + (GWCON) prompt, respectively, followed by the feature number or short name. For example:
Config> feature self learning ip
Self Learning IP configuration
Self Learning IP Config>
Table 15 lists the available feature numbers and names.
Once you access the configuration or operating prompt for a feature, you can begin entering specific commands for the feature. To return to the previous prompt level, enter the exit command at the feature's prompt.
This section describes how to access the protocol configuration and operating processes.
To enter the desired protocol configuration process from the CONFIG> prompt:
Config> protocol SNMP
or
Config> protocol 11 SNMP user configuration
The protocol configuration prompt then displays on the console. The following example shows the SNMP protocol configuration prompt:
SNMP config>
You can now begin entering the protocol's configuration commands. See the corresponding protocol section of the Protocols and Features for more information on specific protocol configuration commands.
In summary, the protocol command lets you enter the configuration process for the protocol software installed in your device. The protocol command enters a protocol's command process. After entering the protocol command, the prompt of the specified protocol appears. From the prompt, you can enter commands specific to that protocol.
To enter a protocol console process from the GWCON prompt:
+ configuration Num Name Protocol 11 SNMP Simple Network Management Protocol 23 ASRT Adaptive Source Routing Transparent Enhanced Bridge 29 MPOA Multi-Protocol Over ATM Num Name Feature 6 QOS Quality of Service 17 Self Self Learning IP 18 RMON Remote Network Monitor 64 Total Networks: Net Interface MAC/Data-Link Hardware State 0 Eth/0 Ethernet/IEEE 802.3 10/100 Ethernet Up 1 Eth/1 Ethernet/IEEE 802.3 10/100 Ethernet Up 2 Eth/2 Ethernet/IEEE 802.3 10/100 Ethernet Up 3 Eth/3 Ethernet/IEEE 802.3 10/100 Ethernet Up 4 Eth/4 Ethernet/IEEE 802.3 10/100 Ethernet Up 5 Eth/5 Ethernet/IEEE 802.3 10/100 Ethernet Up 6 Eth/6 Ethernet/IEEE 802.3 10/100 Ethernet Up 7 Eth/7 Ethernet/IEEE 802.3 10/100 Ethernet Up 8 Eth/8 Ethernet/IEEE 802.3 10/100 Ethernet Up 9 Eth/9 Ethernet/IEEE 802.3 10/100 Ethernet Up 10 Eth/10 Ethernet/IEEE 802.3 10/100 Ethernet Up 11 Eth/11 Ethernet/IEEE 802.3 10/100 Ethernet Up 12 Eth/12 Ethernet/IEEE 802.3 10/100 Ethernet Up 13 Eth/13 Ethernet/IEEE 802.3 10/100 Ethernet Up 14 Eth/14 Ethernet/IEEE 802.3 10/100 Ethernet Up 15 Eth/15 Ethernet/IEEE 802.3 10/100 Ethernet Up 16 Eth/16 Ethernet/IEEE 802.3 10/100 Ethernet Up 17 Eth/17 Ethernet/IEEE 802.3 10/100 Ethernet Up 17 Eth/18 Ethernet/IEEE 802.3 10/100 Ethernet Up 19 Eth/19 Ethernet/IEEE 802.3 10/100 Ethernet Up 20 Eth/20 Ethernet/IEEE 802.3 10/100 Ethernet Up 21 Eth/21 Ethernet/IEEE 802.3 10/100 Ethernet Up 22 Eth/22 Ethernet/IEEE 802.3 10/100 Ethernet Up 23 Eth/23 Ethernet/IEEE 802.3 10/100 Ethernet Up 24 Eth/24 Ethernet/IEEE 802.3 10/100 Ethernet Up 25 Eth/25 Ethernet/IEEE 802.3 10/100 Ethernet Up 26 Eth/26 Ethernet/IEEE 802.3 10/100 Ethernet Up 27 Eth/27 Ethernet/IEEE 802.3 10/100 Ethernet Up 28 Eth/28 Ethernet/IEEE 802.3 10/100 Ethernet Up 29 Eth/29 Ethernet/IEEE 802.3 10/100 Ethernet Up 30 Eth/30 Ethernet/IEEE 802.3 10/100 Ethernet Up 31 Eth/31 Ethernet/IEEE 802.3 10/100 Ethernet Up 32 Eth/31 Ethernet/IEEE 802.3 10/100 Ethernet Up 33 Eth/31 Ethernet/IEEE 802.3 10/100 Ethernet Up 34 Eth/31 Ethernet/IEEE 802.3 10/100 Ethernet Up 35 Eth/31 Ethernet/IEEE 802.3 10/100 Ethernet Up 36 ATM/0 ATM ATM Up 37 ATM/1 ATM ATM Up 38 ATM/2 ATM ATM Down 39 ATM/3 ATM ATM Down 40 Eth/32 Ethernet/IEEE 802.3 ATM Up 41 Eth/33 Ethernet/IEEE 802.3 ATM Up 42 Eth/34 Ethernet/IEEE 802.3 ATM Up 43 Eth/35 Ethernet/IEEE 802.3 ATM Up 44 Eth/36 Ethernet/IEEE 802.3 ATM Up 45 Eth/37 Ethernet/IEEE 802.3 ATM Up 46 Eth/38 Ethernet/IEEE 802.3 ATM Up 47 Eth/39 Ethernet/IEEE 802.3 ATM Up 48 Eth/40 Ethernet/IEEE 802.3 ATM Up 49 Eth/41 Ethernet/IEEE 802.3 ATM Up
50 Eth/42 Ethernet/IEEE 802.3 ATM Up 51 Eth/43 Ethernet/IEEE 802.3 ATM Up 52 Eth/44 Ethernet/IEEE 802.3 ATM Up 53 Eth/45 Ethernet/IEEE 802.3 ATM Up 54 Eth/46 Ethernet/IEEE 802.3 ATM Up 55 Eth/47 Ethernet/IEEE 802.3 ATM Up 56 Eth/48 Ethernet/IEEE 802.3 ATM Up 57 Eth/49 Ethernet/IEEE 802.3 ATM Up 58 Eth/50 Ethernet/IEEE 802.3 ATM Up 59 Eth/51 Ethernet/IEEE 802.3 ATM Up 60 Eth/52 Ethernet/IEEE 802.3 ATM Up 61 Eth/53 Ethernet/IEEE 802.3 ATM Up 62 Eth/54 Ethernet/IEEE 802.3 ATM Up 63 Eth/55 Ethernet/IEEE 802.3 ATM Up
In the following example, the command has been entered for accessing the SNMP protocol console process.
+ protocol 11
or
+ protocol SNMP
The protocol console prompt then displays on the console. This example shows the SNMP protocol console prompt:
SNMP>
You can now begin entering the protocol's commands. See the corresponding protocol section of the Protocols and Features for more information on specific protocol console commands.
The automatic command completion function assists you with the syntax for commands entered at the command line.
To illustrate the behavior of Command Completion, assume that the following commands are allowed in a given menu context. (This is an example menu only.)
caching
cache-timeout
priority
The following online help is available when command-completion is enabled.
See page *** for the enable command-completion syntax.
The following rules apply to automatic command completion:
The following online help is available when command-completion is disabled:
Command Completion is currently Disabled. To Enable this option, use the enable command-completion command from Configuration talk 6.
The Command History contains up to the last 50 commands entered by the user in OPCON, GWCON (Talk 5) or CONFIG (Talk 6) command line menus.
Backward and Forward retrieve keys can be used to recall previously entered commands. In addition, a facility is provided to enable the advanced user to repeat a particular series of commands.
By pressing Ctrl-B (backward) or Ctrl-F (forward) at any command line prompt in an OPCON, GWCON or CONFIG menu, the current command line is replaced by the previous or next command in the Command History. The Command History is common across the command line interface. That is, a command entered while in a GWCON menu can be retrieved from within CONFIG and a command entered while in a CONFIG menu can be retrieved from within GWCON.
When automatic Command Completion is enabled (See"Command Completion") and a Command History retrieve key (Ctrl-B,F,N) is pressed, the Command History is scanned for a command that successfully parses in the current command context. A tone will be sounded if no such command exists.
The Command History contains the most recently entered commands, up to a maximum of the last 50 commands. If only three commands have been entered since a reload, pressing Ctrl-F or Ctrl-B circles through only those three commands. If no commands have been entered thus far, Ctrl-F or Ctrl-B results in tone sound.
| Note: | A command aborted by pressing Ctrl-U will not be entered into the Command History. When Command Completion is enabled, only complete commands are entered into the Command History. |
To enter two similar commands:
display sub les
display sub lec
Enter:
display sub les, then press Enter
Ctrl-B for Backward, and the current line is replaced with-
display sub les
Press Backspace and replace "s" with "c" to get
display sub lec and then press Enter
There is an additional feature for advanced users to facilitate repeating a particular series of GWCON or CONFIG commands. C1, C2,...,Cn in the Command History is referred to as a repeat sequence. This feature may be more convenient than simply using Ctrl-B and Ctrl-F when you must repeat a given task that requires multiple commands. Enter Ctrl-R (repeat) to set the start of the repeat sequence at command C1. Enter Ctrl-N (next) successively to retrieve the next command in the repeat sequence. Commands are not automatically entered, but are placed on the current command line allowing you to modify or enter the command.
To produce the desired behavior of a repeat sequence, the first command retrieved using the first Ctrl-N (next) depends on the manner in which the start of the repeat sequence was set using Ctrl-R (repeat).
Setting the start of the repeat sequence with Ctrl-R can be done in two ways:
If you enter Ctrl-R as command C1 is being keyed in, and then enter commands C2, C3... Cn. Ctrl-N will successively bring commands C1, C2, ... Cn, C1, C2, ... Cn, C1, ... to the command line.
In Example 1, the start of the repeat sequence is set as the first command is keyed in. The user knows ahead of time that the same commands to be entered in GWCON need to be repeated in CONFIG.
Example 1
*console +event Ctrl-R
then press Enter to set the start of the repeat sequence.
Event Logging System user console ELS>display sub les ELS>display sub lec ELS>exit +
Ctrl-P (the default OPCON intercept character) and go to CONFIG.
+-press Ctrl-P- *configuration Config>Ctrl-N for NEXT to retrieve the start of this sequence- Config>event Enter Event Logging System user configuration ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>display sub les Enter ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>display sub lec Enter ELS config>Ctrl-N for NEXT to retrieve the next command in sequence- ELS config>exit Enter Config>
On the other hand, if you first enter C1, C2, ... Cn, and retrieve C1 via Ctrl-B or Ctrl-F. Entering Ctrl-R, entering Ctrl-N successively brings commands C2,..., Cn, C1, C2,..., Cn, C1,...,Cn to the command line (see Example 2). The first occurrence of C1 is bypassed since C1 is already available on the command line at the time it was retrieved, and does not need to be recalled again by the first Ctrl-N.
In Example 2, all the commands are entered and then the first command in the sequence to be repeated is retrieved. A sequence of commands has been entered in GWCON, and the same sequence needs to be repeated in CONFIG.
Example 2
*console +event Event Logging System user console ELS>display sub les ELS>display sub lec ELS>exit +
+Ctrl-P-
*configuration
Config>Ctrl-B four times to retrieve the start of
the four command sequence in this example-
Config>event
Config>event Ctrl-R for REPEAT to set the start of the repeat sequence-
Config>event Enter
Event Logging System user configuration
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>display sub les Enter
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>display sub lec Enter
ELS config>Ctrl-N for NEXT to retrieve the next command in sequence-
ELS config>exit Enter
Config>